41 research outputs found

    Evolving database systems : a persistent view

    Get PDF
    Submitted to POS7 This work was supported in St Andrews by EPSRC Grant GR/J67611 "Delivering the Benefits of Persistence"Orthogonal persistence ensures that information will exist for as long as it is useful, for which it must have the ability to evolve with the growing needs of the application systems that use it. This may involve evolution of the data, meta-data, programs and applications, as well as the users' perception of what the information models. The need for evolution has been well recognised in the traditional (data processing) database community and the cost of failing to evolve can be gauged by the resources being invested in interfacing with legacy systems. Zdonik has identified new classes of application, such as scientific, financial and hypermedia, that require new approaches to evolution. These applications are characterised by their need to store large amounts of data whose structure must evolve as it is discovered by the applications that use it. This requires that the data be mapped dynamically to an evolving schema. Here, we discuss the problems of evolution in these new classes of application within an orthogonally persistent environment and outline some approaches to these problems.Postprin

    Incremental database systems

    No full text

    Inheritance as an Incremental Modeification Mechanism of What Like is and Isn't Like

    No full text
    ion", Data Types and Persistence, Springer-Verlag, Heidelberg, pp. 31 - 42, 1988. 10. Cardelli, L. and Wegner, P. "On Understanding Types, Data Abstraction and Polymorphism", Association for Computing Machinery Computing Surveys, vol 17, 4, pp. 471 - 523, 1985. 11. Connor, R. C. H. "Types and Polymorphism in Persistent Programming Systems", Ph. D. Thesis, St Andrews, 1990. 12. Connor, R. C. H., Brown, A. B., Cutts, Q. I., Dearle, A., Morrison, R. and Rosenberg, J. "Type Equivalence Checking in Persistent Object Systems", Implementing Persistent Object Bases, Morgan Kaufmann, pp. 151 - 164, 1990. 13. Connor, R. C. H., McNally, D. J. and Morrison, R. "Subtyping and Assignment in Database Programming Languages", Proc. 3rd International Workshop on Database Programming Languages,1991, Morgan Kaufmann, To appear. 14. Jones, A. K. and Liskov, B. "A Language Extension for Expressing Constraints on Data Access", Communications of the Association for Computing Machinery, vol 21, 5, pp. 358 - 36..

    Evolving database systems:a persistent view

    No full text
    Orthogonal persistence ensures that information will exist for as long as it is useful, for which it must have the ability to evolve with the growing needs of the application systems that use it. This may involve evolution of the data, meta-data, programs and applications, as well as the users' perception of what the information models. The need for evolution has been well recognised in the traditional (data processing) database community and the cost of failing to evolve can be gauged by the resources being invested in interfacing with legacy systems. Zdonik has identified new classes of application, such as scientific, financial and hypermedia, that require new approaches to evolution. These applications are characterised by their need to store large amounts of data whose structure must evolve as it is discovered by the applications that use it. This requires that the data be mapped dynamically to an evolving schema. Here, we discuss the problems of evolution in these new classes of application within an orthogonally persistent environment and outline some approaches to these problems

    Evolving Database Systems: A Persistent View

    No full text
    Orthogonal persistence ensures that information will exist for as long as it is useful, for which it must have the ability to evolve with the growing needs of the application systems that use it. This may involve evolution of the data, meta-data, programs and applications, as well as the users ’ perception of what the information models. The need for evolution has been well recognised in the traditional (data processing) database community and the cost of failing to evolve can be gauged by the resources being invested in interfacing with legacy systems. Zdonik has identified new classes of application, such as scientific, financial and hypermedia, that require new approaches to evolution. These applications are characterised by their need to store large amounts of data whose structure must evolve as it is discovered by the applications that use it. This requires that the data be mapped dynamically to an evolving schema. Here, we discuss the problems of evolution in these new classes of application within an orthogonally persistent environment and outline some approaches to these problems

    LLO

    No full text

    Extending the scope of database services

    No full text
    corecore